Fixes for methods that use raw sql to work properly with scopes that use joins #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
December 17, 2010 15:48
… use joins by including the table name in the condition sql.
…operly with scopes that use joins by including the table name in the condition sql.
|
Second this! |
|
This would be great. |
|
please merge this! |
|
@stefankroes, could you merge this? :) |
|
sorry for the long wait. merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because the descendants, subtree and subtree.arrange methods use raw sql as part of their conditions, using them with another scope method breaks if that scope uses joins. These commit fix that by adding the table name to the sql. Any other instances I find like this that break joins, I'll commit to this branch.